Thanks for your pull request to Laravel!

Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.

If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!

If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.

@taylorotwell Hi 😄
All other methods like have the Not variant

whereIn() and whereNotIn()
orWhereIn() and orWhereNotIn()
whereNull() and whereNotNull()
orWhereNull() and orWhereNotNull()
whereExists() and whereNotExists()
orWhereExists() and orWhereNotExists()
whereBetween() and whereNotBetween()
orWhereBetween() and orWhereNotBetween()

So it's only logical to add the simple Not variant to where() and orWhere()
If you could give this a thought that would be cool

I agree, it would be cleaner.

doing :

->where('field', '!=', 'someValue');

all the time. whereNot('field', 'someValue') would be more readable

it's more of a syntactic sugar than anything

@lk77
It's not a syntactic sugar it's actually a valid sql thing, in sql you can do a not
https://dev.mysql.com/doc/refman/8.0/en/logical-operators.html

I'm actually using this for negating a group of wheres

where not ( condition and condition and condition and condition )

@taylorotwell Is there any chance for this to get reconsidered? We've run into use-cases for this multiple times since we first saw this a month ago, and I'm sure we're not alone about that.